Skip to content

Add labeler #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yamcodes merged 2 commits into from
Jan 17, 2026
Merged

Add labeler #218

yamcodes merged 2 commits into from
Jan 17, 2026

Conversation

@yamcodes
Copy link
Owner

@yamcodes yamcodes commented Jan 17, 2026 •
edited by coderabbitai bot
Loading

Description

Closes #214

PR Checklist

  • Read the Developer's Guide in CONTRIBUTING.md
  • Use a concise title to represent the changes introduced in this PR
  • Provide a detailed description of the changes introduced in this PR, and, if necessary, some screenshots
  • Reference an issue or discussion where the feature or changes have been previously discussed
  • Add a failing test that passes with the changes introduced in this PR, or explain why it's not feasible
  • Add documentation for the feature or changes introduced in this PR to the docs; you can run them with bun docs

Summary by CodeRabbit

  • Chores
    • Added an automated pull request labeling system and CI workflow to tag PRs by project area (frontend apps, docs, tests, CI/workflows). Labels are applied automatically on PRs to improve organization and review routing.

✏️ Tip: You can customize this high-level summary in your review settings.

@yamcodes yamcodes linked an issue Jan 17, 2026 that may be closed by this pull request
Add labeler #214
Closed
3 tasks
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 17, 2026 •
edited
Loading

Caution

Review failed

The pull request is closed.

Walkthrough

Adds GitHub PR labeling: a labeler configuration mapping file globs to labels and a GitHub Actions workflow that runs the labeler on pull_request_target events.

Changes

Cohort / File(s) Summary
Labeler Configuration
​.github/labeler.yml		 New label rules mapping globs to labels: apps/conduit/** → conduit, apps/www/** → www, **/*.md → docs, **/*.test.ts / **/*.test.tsx → tests, and .github/**/* → github actions.
Labeler Workflow
​.github/workflows/labeler.yml		 New GitHub Actions workflow "Pull Request Labeler" triggered on pull_request_target, runs on ubuntu-latest, reads repo contents and executes actions/labeler@v6 with sync-labels: true.

Sequence Diagram(s)

sequenceDiagram
  participant PR as Pull Request
  participant GH as GitHub Actions (runner)
  participant Repo as Repository (files)
  participant Labeler as actions/labeler@v6

  PR->>GH: open/update PR (pull_request_target)
  GH->>Repo: read `.github/labeler.yml`
  GH->>Labeler: execute labeler with repo content
  Labeler->>Repo: evaluate changed files against globs
  Labeler->>GH: request apply/update labels on PR
  GH->>PR: apply labels
Loading

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • Add labeler #218 — Adds the same .github/labeler.yml and .github/workflows/labeler.yml files; directly related.

Poem

🐰 I hopped through files both near and far,
New labels to guide each PR like a star.
Conduit and www find their lane,
Docs and tests tagged without strain.
Hooray—automation hops in with a cheer!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add labeler' is concise and directly describes the main change—adding a GitHub PR labeler configuration and workflow. It clearly conveys the primary objective of the changeset.
Linked Issues check ✅ Passed The PR implements the labeler feature requested in issue #214 by adding the labeler configuration (.github/labeler.yml) and workflow (.github/workflows/labeler.yml) as suggested.
Out of Scope Changes check ✅ Passed All changes are directly related to implementing the labeler feature. The two files added (.github/labeler.yml and .github/workflows/labeler.yml) are focused on the labeling functionality with no extraneous modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

coderabbitai[bot]
coderabbitai bot requested changes Jan 17, 2026
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents 
In @.github/labeler.yml:
- Around line 20-22: The glob pattern "**/.github/**/*" is too broad and only
matches .github directories at any depth; update the changed-files pattern under
the "github actions" labeler entry to target the repository root .github
directory by replacing "**/.github/**/*" with either ".github/**/*" or
".github/**" so the root .github files are matched as intended.

@yamcodes yamcodes merged commit dca479e into main Jan 17, 2026
7 of 8 checks passed
@yamcodes yamcodes deleted the 214-add-labeler branch January 17, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Add labeler

2 participants

@yamcodes